Control, events and programming
The driver gives you the 2N in three places: on the tile, as programming actions you can call, and as programming events you can react to.
The tile​
The driver's tile appears on the home and room pages, with a status line showing the connection state. Opening it shows the 2N Doorstation control page:
- Switches — a Switch n On and Switch n Off button for each of switches 1–4. On energises the 2N switch (releasing a strike or closing a relay); Off de-energises it.
- Inputs — a live line per digital input showing Input n Open or Input n Closed.
- Call Control — Call Panels dials the Crestron touch panels, and End Call ends the call.
The tile always renders, but the Switch, Call Panels and End Call actions do nothing until the driver is licensed. Input state and events still update.
Programming actions​
In Crestron Home programming, this device exposes actions you can call from a scene, a schedule or a rule:
| Action | What it does |
|---|---|
switch1On … switch4On | Energise switch 1–4 (release the strike / close the relay). |
switch1Off … switch4Off | De-energise switch 1–4. |
dialPanels | Place a call to the Crestron touch panels. |
dialCustom | Place a call to a custom target you pass in (a SIP / RAVA destination). |
endDialPanels | End the calls this driver placed. |
endAllSipCalls | End all active SIP calls on the 2N. |
Programming events​
The driver raises events from the 2N's event log. Bind a scene, a notification or a rule to any of them:
| Event | Fires when |
|---|---|
switch1Activated / switch1Deactivated … switch4… | A switch is energised / de-energised (from anywhere — the tile, programming, or the 2N itself). |
input1Opened / input1Closed … input4… | A digital input opens / closes. |
relay1Activated / relay1Deactivated | The 2N's relay changes state. |
output1Activated / output1Deactivated | The 2N's output changes state. |
motionDetected | The 2N reports motion. |
noiseDetected | The 2N reports noise. |
callButtonPressed | A quick-dial / call button on the 2N is pressed. |
Because the events come from the device's event log, a switch or input event fires whether the change was made from the tile, from Crestron programming, or directly on the 2N (a keypad code, a REX button). Bind to the event, not just to your own action, to catch every case.